docs: clarify AssetAlias usage#67392
Open
Will-thom wants to merge 1 commit into
Open
Conversation
bugraoz93
approved these changes
May 24, 2026
Lee-W
approved these changes
Jun 10, 2026
| Dynamic data events emitting and asset creation through AssetAlias | ||
| ----------------------------------------------------------------------- | ||
| An asset alias can be used to emit asset events of assets with association to the aliases. Downstreams can depend on resolved asset. This feature allows you to define complex dependencies for Dag executions based on asset updates. | ||
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is |
Member
There was a problem hiding this comment.
Suggested change
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is | |
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset attributes (i.e., URI, name) are |
Contributor
There was a problem hiding this comment.
imo we should not use "i.e.". What about
Use
AssetAliaswhen a task must declare an asset dependency before the Asset's fixed attributes (like URI or name) are available.
Member
There was a problem hiding this comment.
as lone as we use both name and uri, I'm good 👀
RNHTTR
reviewed
Jun 11, 2026
| ----------------------------------------------------------------------- | ||
| An asset alias can be used to emit asset events of assets with association to the aliases. Downstreams can depend on resolved asset. This feature allows you to define complex dependencies for Dag executions based on asset updates. | ||
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is | ||
| known. The alias is listed in ``outlets`` as a stable name, and the task resolves it at runtime by |
Contributor
There was a problem hiding this comment.
What does "stable name" mean? What does "concrete" mean?
| Use ``AssetAlias`` when a task must declare an asset dependency before the concrete asset URI is | ||
| known. The alias is listed in ``outlets`` as a stable name, and the task resolves it at runtime by | ||
| adding one or more concrete ``Asset`` objects through ``outlet_events`` or yielded ``Metadata``. | ||
| Downstream Dags can depend on the alias, and Airflow triggers them when events are emitted for the |
Contributor
There was a problem hiding this comment.
"trigger" is kind of an overloaded term in Airflow. Maybe we should say "...and Airflow initiates a Dag run when..."
Contributor
|
@Will-thom can you resolve open conversations? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #52250. Clarifies when to use AssetAlias: when the concrete asset URI is only known at runtime, while the task still needs to declare a stable outlet dependency. Validation: git diff --check for airflow-core/docs/authoring-and-scheduling/assets.rst and targeted text search.
Important
🛠️ Maintainer triage note for @Will-thom · by
@potiuk· 2026-06-17 18:53 UTCSome review feedback from
Lee-W,RNHTTRis waiting on you:The ball is in your court — you've been assigned to this PR. Reply or push a fix in each thread, then mark them resolved.
Automated triage — may be imperfect; a maintainer takes the next look.